翻訳と辞書
Words near each other
・ Soga language
・ Soga Maina
・ Soga no Emishi
・ Soga no Iname
・ Soga no Iruka
・ Soga no Kitashihime
・ Soga no Koma
・ Soga no Kurayamada no Ishikawa no Maro
・ Soga no Umako
・ Soga Ryōjin
・ Soga Sambo
・ Soga Shōhaku
・ Soga Station
・ SOGA1
・ Software sampler
Software security assurance
・ Software Shelf International
・ Software sizing
・ Software Spectrum
・ Software standard
・ Software Star
・ Software studies
・ Software suite
・ Software Sustainability Institute
・ Software synthesizer
・ Software system
・ Software system safety
・ Software taggant
・ Software technical review
・ Software Technology Parks of India


Dictionary Lists
翻訳と辞書 辞書検索 [ 開発暫定版 ]
スポンサード リンク

Software security assurance : ウィキペディア英語版
Software security assurance

Software security assurance is a process that helps design and implement software that protects the data and resources contained in and controlled by that software. Software is itself a resource and thus must be afforded appropriate security.
Since the number of threats specifically targeting software is increasing, the security of our software that we produce or procure must be assured. "Dependence on information technology makes software assurance a key element of business
continuity, national security, and homeland security."〔Karen Mercedes, Theodore Winograd ("Enhancing The Development Life Cycle To Produce Secure Software" ), ''Data & Analysis Center for Software'', October 2008〕
== What is software security assurance? ==
Software Security Assurance (SSA) is the process of ensuring that software is designed to operate at a level of security that is consistent with the potential harm that could result from the loss, inaccuracy, alteration, unavailability, or misuse of the data and resources that it uses, controls, and protects.
The software security assurance process begins by identifying and categorizing the information that is to be contained in, or used by, the software. The information should be categorized according to its sensitivity. For example, in the lowest category, the impact of a security violation is minimal (i.e. the impact on the software owner's mission, functions, or reputation is negligible). For a top category, however, the impact may pose a threat to human life; may have an irreparable impact on software owner's missions, functions, image, or reputation; or may result in the loss of significant assets or resources.
Once the information is categorized, security requirements can be developed. The security requirements should address access control, including network access and physical access; data management and data access; environmental controls (power, air conditioning, etc.) and off-line storage; human resource security; and audit trails and usage records.

抄文引用元・出典: フリー百科事典『 ウィキペディア(Wikipedia)
ウィキペディアで「Software security assurance」の詳細全文を読む



スポンサード リンク
翻訳と辞書 : 翻訳のためのインターネットリソース

Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.